The Goal of Deployment
System development will usually take place in isolated systems owned and operated by the development company.
Once testing has been completed, the system must then be migrated and deployed to the target devices, systems, and locations as required,
at which point it can be handed over to the client. This phase is often referred to as the Installation phase.
Key Deployment Activities
Depending on the project, some or all of the following tasks will take place:
๐ฅ๏ธ Physical & Cloud Setup
- Installation of physical infrastructure: If the system relies on local, on-premises hardware, this is installed first. Hardware is often prepared while the software is in final testing to avoid delays.
- Set up and configuration of cloud-based infrastructure: Hardware is connected to cloud services. Developers ensure the new hardware is configured so it can connect to third-party services without issue.
๐พ Software & People
- Installation and deployment of software components: Any new software systems that have been developed are now installed onto the target machines ready for use.
- End-user training: Before the system goes live, stakeholders are trained on how to use it. They are divided into groups and trained only on the area they interact with. In-house IT staff receive training on a much wider range of aspects, including troubleshooting.
Why C is correct: The text explicitly lists "End-user training" as a key activity under the Installation phase: "Before a system goes live, the development company will provide key stakeholders with training on how to use the system."
Coding and translating designs are Implementation tasks. Identifying bugs is part of the Testing phase.
The Goal of Maintenance
Once the system is deployed, the project moves to the Maintenance phase.
During this phase, the development team will provide ongoing support for the organization on an already deployed product.
In the early stages of deployment, maintenance will focus on identifying any issues or bugs that were not identified during testing and installation.
As a product becomes more established, the monitoring will become less frequent and focus will be on evaluating whether the product still meets user and business needs in changing situations and environments.
Why B is correct: The text states: "In the early stages of deployment, maintenance will focus on identifying any issues or bugs... As a product becomes more established, the monitoring will become less frequent and focus will be on evaluating whether the product still meets user and business needs in changing situations and environments."
Key Maintenance Activities
Some of the key activities in the maintenance phase include:
๐ Fixing & Optimizing
- Bug fixing: Systems encounter situations that could not be replicated in testing. Users report issues, which are analyzed and prioritized based on severity. (Often governed by an SLA contract).
- Performance optimization: Improving working systems to provide streamlined processes and make users more productive.
๐ Updating & Evolving
- Security updates: Applying patches and updates to protect against new and emerging threats.
- New feature implementation: Adding new features to existing systems where possible, rather than starting completely new projects, to save time, money, and reduce training burdens.
- Documentation updates: Keeping user guides and technical documentation up-to-date to reflect changes.
Why D is correct: The text explicitly lists "New feature implementation" as a maintenance activity: "where possible it is preferable to add additional features to existing systems. This also reduces the training burden as users will already be familiar with how the rest of the system works."
Bug fixing, performance optimization, security updates, and documentation updates are all separate maintenance tasks.
๐ You've mastered the Deployment and Maintenance Phases!
Recap:
โข Deployment: Install physical/cloud infrastructure, load software, and train end-users.
โข Maintenance: Ongoing support for bug fixing, performance, security, and new features.
โข Evolution: Adding features to existing systems is often preferred over starting from scratch.
You have now covered the entire Waterfall Lifecycle. Great job!